Subject: Re: SAS C 6.0 weirdness with __inline
From: [email-masked] (Doug Walker)
Date: 19 Oct 92 19:23:19 GMT
Newsgroups: comp.sys.amiga.programmer

In article <[email-masked]>, [email-masked] (Doug Walker) writes:
|> This is not a bug.  The inlining is performed by the global optimizer.
|> Hence, if you don't run the global optimizer, you don't get inlining.
|> You will need to declare a "real" version of the function to compile
|> without the global optimizer in this case.
|> 

Oops, I was wrong.  I double-checked the code to make sure, and
it looks like the intent is to generate code for the __inline
functions so they will work even if GO is not run.  This does
not seem to be working correctly.

Until a fix is available, you'll need to create a callable version
of the function (one without the __inline keyword) and link that
in.  A convenient way to do this is to put it in a seperate .o
file, then use the LIB keyword on SC or SLINK to link it into
your program.  This way, if inlining has been done, it won't
get linked in; if not, it will get linked in.

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: [email-masked]                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.